infrastructure/eid-wallet/src/routes/(app)/main/+page.svelte (1)

186-201: 💤 Low value

Consider adding error logging for consistency with other loaders.

The other data loaders (loadBindingDocuments, loadPersonalIntoStore) wrap their logic in try/catch and log warnings on failure. While the upstream controller getters have internal .catch() handlers that return undefined, adding a similar pattern here would provide consistent diagnostics.

♻️ Optional: Add try/catch for consistency

 async function loadUserInfo(): Promise<void> {
     if (!globalState) return;
+    try {
         const [userInfo, fake, vaultData] = await Promise.all([
             globalState.userController.user,
             globalState.userController.isFake,
             globalState.vaultController.vault,
         ]);
         isFake = fake;
         cachedIsFake = fake;
         userData = { ...userInfo, isFake: fake };
         cachedUserData = userData;
         if (vaultData?.ename) {
             ename = vaultData.ename;
             cachedEname = ename;
         }
+    } catch (err) {
+        console.warn("[main] Failed to load user info:", err);
+    }
 }

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@infrastructure/eid-wallet/src/routes/`(app)/main/+page.svelte around lines
186 - 201, Wrap the body of loadUserInfo in a try/catch similar to
loadBindingDocuments/loadPersonalIntoStore: call the same Promise.all on
globalState.userController.user, globalState.userController.isFake, and
globalState.vaultController.vault inside a try block, and in the catch log a
warning with context (e.g., "loadUserInfo failed" plus the caught error) so
failures are diagnosable but don’t throw; preserve the existing assignments to
isFake, cachedIsFake, userData, cachedUserData, ename and cachedEname when the
Promise.all succeeds.